No Current Link To VocabularyCoded With ExtensionsCoded No Extensions
COCT_MT090108CA
Assigned Person identified-informational

Derived from RMIM: _ and HMD: _
 
AssignedEntity

Design Comments:

The person organization assigned to carry out the associated (linked by a participation) action and/or the organization under whose authority they are acting.

UsageNotes:

All attributes other than the various identifiers are expected to be retrieved from the provider registry.

Rationale:

Critical to tracking responsibility and performing follow-up. The CMET supports both licensed providers as well as non-licensed providers such as technicians, receptionists, etc.

classCode [1..1] (M)
Role (CS) {CNE:C:RoleClass:ASSIGNED, fixed value= "ASSIGNED"}
id [1..3] (M)
Role (II.BUS)

Design Comments:

Unique identifier the person involved in the action.

Rationale:

Allows unique identification of the person which can be critical for authentication, permissions, drill-down and traceability and is therefore mandatory.

code [1..1]
Role (CV) {CNE:D:HealthcareProviderRoleType}

Design Comments:

Indicates the "kind" of healthcare participant, such as "physician", "dentist", "lab technician", "receptionist", etc.

Rationale:

Provides context around the actions of the participant and is therefore mandatory.

telecom [0..5]
Role (LIST<TEL.PHONEMAIL>)

Design Comments:

Indicates phone and/or e-mail addresses at which the healthcare worker can be reached.

Rationale:

This is the most commonly used piece of contact information and is returned here to avoid unnecessary queries of the provider registry.

assignedPerson [1..1] (Person)
representedOrganization [0..1] (Organization)

Design Comments:

Identifies the organization on whose behalf the action is performed.

Rationale:

Used for determining responsibility and potentially confirming permissions.

 
Person
classCode [1..1] (M)
Person (CS) {CNE:C:EntityClass:PSN, fixed value= "PSN"}
determinerCode [1..1] (M)
Person (CS) {CNE:C:EntityDeterminer:INSTANCE, fixed value= "INSTANCE"}
name [1..1]
Person (PN.BASIC)

Design Comments:

The name of the participating person.

Rationale:

This is a human-readable name and is thus essential for both display and validation of the person. As a result, the attribute is mandatory.

asHealthCareProvider [0..1] (HealthCareProvider)
 
HealthCareProvider
classCode [1..1] (M)
LicensedEntity (CS) {CNE:C:RoleClass:PROV, fixed value= "PROV"}
id [1..1] (M)
LicensedEntity (II.PUBLIC)

Design Comments:

The license number issued to the provider and relevant to the current action.

UsageNotes:

If the identifier used in the root of the CMET is the same as the license number, the license number should be sent in both places.

Detailed information about the status and effective period of licenses must be retrieved from the provider registry.

Rationale:

Allows lookup on college website, confirmation of identity, etc. Regulations occasionally require license numbers to be specified as part of clinical records.

 
Organization

Design Comments:

Identifies the organization on whose behalf the action is performed.

Rationale:

Used for determining responsibility and potentially confirming permissions.

classCode [1..1] (M)
Organization (CS) {CNE:C:EntityClass:ORG, fixed value= "ORG"}
determinerCode [1..1] (M)
Organization (CS) {CNE:C:EntityDeterminer:INSTANCE, fixed value= "INSTANCE"}
id [0..1]
Organization (II.PUBLIC)

Design Comments:

A unique identifier for the organization

Rationale:

Allows the organization to be referenced when determining privileges and for drill-downs to retrieve additional information. Because of its importance, the attribute is mandatory.

name [0..1]
Organization (ST)

Design Comments:

Identifies the name of the organization

Rationale:

Allows for human recognition of the organization as well as confirmation of the identifier. As a result, the attribute is mandatory.